Subject: more comments to Jeffs new proposal

From: [email-masked]
Date: Thu, 28 Jul 94 12:24:09 +0100

Here are some more comments to Jeff's new proposal for mapped conversations.

- If the map_name is a 1-64 character name, we need an additional
  parameter map_name_length in all CPI-C calls containing map_name.
  An alternative would be to define the map name as an 8 byte
  character string (similiar to sym_dest_name).

- Page 3 of the proposal contains the SET_MAP_NAME and EXTRACT_MAP_NAME
  calls from the former proposal.

- In an OSI TP environment the encode/decode routine must know the abstract
  syntax and the transfer syntax. Since the transfer syntax is negotiated
  between the two application entities CPI-C users cannot know the
  transfer syntax.
  A possible implementation would be:
  The system administrator configures map_names. To each map_name he
  assigns an encode/decode routine and an abstract syntax name.
  The encode routine can find out the abstract syntax from the map_name.
  The routine must ask the CRM which transfer syntax was negotiated
  on this association for this abstract syntax. Then the routine can
  make the encoding.
  The decode routine gets the transfer syntax and abstract syntax from
  the CRM. The CRM finds out the map_name from the abstract syntax and
  gives it to the CPI-C user.
  Do I have the right understanding? Are there other possible implementations?
  I think the CPI-C document should contain some sentences like these.

- We need a description of the new return_code values in appendix B.

Peter Binninger

-----------------------------------------------------------------------------
Peter Binninger                         Voice: (+49) 7531-87-4758
Computer Gesellschaft Konstanz mbH      Fax:   (+49) 7531-87-4888
(Siemens Nixdorf Informationssysteme)   Email: [email-masked]
Max-Stromeyer-Strasse 116
78467 Konstanz
Germany